Skip to content

docs: add CONTRIBUTING, SECURITY and .clang-format#913

Open
Aswinmcw wants to merge 1 commit into
Multicorewareinc:masterfrom
Aswinmcw:docs/add-contributing-security-clang-format
Open

docs: add CONTRIBUTING, SECURITY and .clang-format#913
Aswinmcw wants to merge 1 commit into
Multicorewareinc:masterfrom
Aswinmcw:docs/add-contributing-security-clang-format

Conversation

@Aswinmcw

@Aswinmcw Aswinmcw commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

What

Adds three contributor-onboarding / project-hygiene files that did not exist in the repository:

  • CONTRIBUTING.md — build instructions (Linux/macOS/Windows, plus 8/10/12-bit and multilib), how to run TestBench and the regression suites, coding style, commit-message and PR conventions, guidance for assembly/SIMD contributions, and dual-licensing terms.
  • SECURITY.md — a private vulnerability-disclosure policy. x265 parses untrusted input (YUV/Y4M, CLI/config params, HDR10+ metadata) and is embedded widely as libx265, so a coordinated-disclosure channel is valuable; there was none before.
  • .clang-format — mirrors exactly the style the "Code Quality" job in .github/workflows/ci.yml generates and enforces (LLVM base, 4-space indent, no tabs, 120-col, Allman braces). Committing it lets contributors reproduce the CI style check locally instead of the canonical config living only inside a CI YAML string.

Why

The repo had no CONTRIBUTING, SECURITY, or committed .clang-format. New contributors had to infer the build matrix, test flow, and style from CI internals and history.

Notes

  • Documentation/config only — no source, build-system, or CI changes; nothing that affects the encoder or the produced binaries.
  • .clang-format is intentionally byte-identical to the CI-generated config, so it introduces no new or conflicting style rules. CI checks only changed lines, so this does not trigger reformatting of existing code.
  • Content was cross-checked against the actual repo: the build/ generator scripts, source/test/ harnesses (TestBench, regression-tests.txt, etc.), doc/uncrustify/codingstyle.cfg, COPYING, and the commit-prefix conventions in git log.

Happy to adjust the security contact address, mailing-list/IRC details, or any wording to match maintainer preference.

@Aswinmcw Aswinmcw force-pushed the docs/add-contributing-security-clang-format branch 2 times, most recently from d80e7e0 to b0aef0e Compare July 9, 2026 09:53
Add contributor-onboarding and security-policy documents, plus a
committed clang-format configuration, none of which existed before.

- CONTRIBUTING.md: build (incl. 8/10/12-bit + multilib), TestBench and
  regression testing, coding style, commit-message and PR conventions,
  guidance for assembly/SIMD contributions, and dual-license terms.
- SECURITY.md: private vulnerability-disclosure policy for a codec that
  parses untrusted input, with reporting channels and scope.
- .clang-format: mirrors exactly the style enforced by the Code Quality
  job in .github/workflows/ci.yml (LLVM base, 4-space, no tabs, 120 col,
  Allman braces) so local runs match CI. Documentation only; no code or
  build changes.
@Aswinmcw Aswinmcw force-pushed the docs/add-contributing-security-clang-format branch from b0aef0e to a0f98ff Compare July 9, 2026 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant